Technologies for route navigation sharing in a community cloud

ABSTRACT

Technologies for sharing route navigation data in a community cloud include a mobile navigation device of a vehicle and a remote mobile navigation device of a remote vehicle. The mobile navigation device generates sensor data associated with a current route of the vehicle and determines whether a reference traffic event occurs within a segment of the current route of the vehicle. In response to a determination that a reference traffic event occurs, the mobile navigation devices transmits route update data to the remote mobile navigation device. Based on the route update data, the remote mobile navigation device updates a current route of the remote vehicle to avoid the reference traffic event within a corresponding segment of the current route of the remote vehicle. The mobile navigation device may also transmit the sensor data to a community compute device, which may transmit route update data to the remote mobile navigation device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/499,154, filed Sep. 27, 2014.

BACKGROUND

Mobile computing devices such as smartphones, tablets, and in-vehicleinfotainment devices typically include applications for navigation,driving directions, or pathfinding. Those applications may use theglobal positioning system (GPS) or other techniques to determine thedevice location. Driving directions and other routes may be determinedby the mobile device or by a server device in communication with themobile device. Directions are typically generated for the route havingthe shortest distance or travel time between two points.

Cloud navigation is an increasingly popular service being offered bymany cloud computing providers (i.e., “cloud service providers”). Suchcloud service providers typically receive location and trafficinformation from a large number of subscriber devices (e.g., in-vehiclenavigation systems, smartphones, etc.) and, based on that information,provide real-time routing to subscribers upon request. However, to takeadvantage of such navigation services, subscribers must typically agreeto the sharing of their personal location information with the cloudservice provider and/or other subscribers. As a result, a portion ofeach subscriber's autonomy and privacy is diminished through the use ofsuch cloud services.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of asystem for sharing route navigation data in a community cloud;

FIG. 2 is a simplified block diagram of at least one embodiment of themobile navigation device of the system of FIG. 1;

FIG. 3 is a simplified block diagram of at least one embodiment of thecommunity compute device of the system of FIG. 1;

FIG. 4 is a simplified block diagram of at least one embodiment of anenvironment of the mobile navigation device of the system of FIG. 1;

FIG. 5 is a simplified block diagram of at least one embodiment of anenvironment of the community compute device of the system of FIG. 1;

FIG. 6 is a simplified flow diagram of at least one embodiment of amethod for sharing route navigation data that may be executed by themobile navigation device of the system of FIG. 1;

FIG. 7 is a simplified flow diagram of at least one embodiment of amethod for sharing route navigation data that may be executed by thecommunity compute device of the system of FIG. 1; and

FIG. 8 is a simplified flow diagram of at least one embodiment of amethod for updating a navigation route that may be executed by themobile navigation device of the system of FIG. 1.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described. Additionally, it should be appreciated that itemsincluded in a list in the form of “at least one of A, B, and C” can mean(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).Similarly, items listed in the form of “at least one of A, B, or C” canmean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon one or more transitory or non-transitory machine-readable (e.g.,computer-readable) storage medium, which may be read and executed by oneor more processors. A machine-readable storage medium may be embodied asany storage device, mechanism, or other physical structure for storingor transmitting information in a form readable by a machine (e.g., avolatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

Referring now to FIGS. 1-3, in an illustrative embodiment, a system 100for route navigation in a community cloud 102 includes a mobilenavigation device 110, one or more remote mobile navigation devices 130,and a community compute device 140. Each of the mobile navigation device110, the remote mobile navigation device(s) 130, and the communitycompute device 140 may be communicatively coupled to any number ofdifferent networks 190. As shown in FIG. 1, the mobile navigation device110 may be included in or otherwise associated with a vehicle 104 andeach of the mobile navigation device(s) 130 may be included in orotherwise associated with one or more remote vehicles 108. In theillustrative embodiment, each of the vehicles 104, 108 is embodied as awheeled passenger vehicle (e.g., a car, truck, truck-tractor, bus,etc.). However, it should be appreciated that, in other embodiments, oneor more of the vehicles 104, 108 may be embodied as another type ofvehicle (e.g., as a rail-driven vehicle, aircraft, maritime vessel,unmanned vehicle, drone, or another vehicle suited for application ofthe described techniques and mechanisms) or other moveable apparatus.

As shown, the mobile navigation device 110, the remote mobile navigationdevice(s) 130, and the community compute device 140 are each members 106of or otherwise form the community cloud 102. Each member of thecommunity cloud 102 is configured to directly communicate or shareinformation with other members of the community cloud 102. As such,information may be shared directly among members of the community cloud102 without requiring the information to be first shared with a publiccloud service provider 170 or other members 162 of a public cloud 160such as, for example, the one or more remote compute devices 180. Itshould be appreciated that by only sharing information with othermembers 106 of the community cloud 102, users may still benefit frominformation obtained from other users without being required to sharetheir own personal information with unknown or untrusted users or cloudservice providers. In that way, privacy may be increased for usershaving devices that are members 106 of the community cloud 102.

In the illustrative embodiment, the mobile navigation device 110, theremote mobile navigation device(s) 130, and the community compute device140 are configured to share vehicle routing or navigation informationwith each other. For example, the mobile navigation device 110 isconfigured to generate sensor data corresponding to a current route ofthe vehicle 104. At least one segment (e.g., a portion, subset, etc.) ofthe current route of the vehicle 104 may be similar to or otherwisecorrespond to one or more segments of a different route (e.g., anexisting route, a commonly traveled route, a future route, etc.) of aremote vehicle 108. In operation, the mobile navigation device 110determines, based on the generated sensor data, whether a referencetraffic event (e.g., an amount of traffic congestion, a type of trafficaccident, an amount or type of roadway construction, a roadwayobstruction, a roadway hazard, etc.) has occurred in the segment of thecurrent route that corresponds to the similar and/or correspondingsegment(s) of the route of the remote vehicle 108. In response to makingsuch a determination, the mobile navigation device 110 of the vehicle104 generates and transmits route update data (e.g., an alternate route,information indicative of an alternate route, etc.) to the remote mobilenavigation device 130 of the remote vehicle 108 (e.g., the remote mobilenavigation device 130 a of the remote vehicle 108 a). In suchembodiments, the remote mobile navigation device 130 of the remotevehicle 108 updates the current route of the remote vehicle 108 to avoidthe segment(s) in which the reference traffic event is determined tohave occurred.

In some embodiments, the mobile navigation device 110 transmits thesensor data corresponding to the current route of the vehicle 104 to thecommunity compute device 140. In such embodiments, the community computedevice 140 may be configured to determine, based on the received sensordata, whether a reference traffic event has occurred within a segment ofthe current route of the vehicle 104. As discussed, the segment of thecurrent route of the vehicle 104 may be similar to or otherwisecorrespond to one or more segments of a different route (e.g., anexisting route, a commonly traveled route, a future route, etc.) of aremote vehicle 108. In response to determining that that a referencetraffic event has occurred within a segment of the current route of thevehicle 104, the community compute device 140 generates and transmitsroute update data to the remote mobile navigation device 130 of theremote vehicle 108 (e.g., the remote mobile navigation device 130 a ofthe remote vehicle 108 a). In such embodiments, the remote mobilenavigation device 130 updates the current route of the remote vehicle108 to avoid the segment(s) in which the reference traffic event isdetermined to have occurred.

The mobile navigation device 110 may be embodied as, or form a portionof, an in-vehicle infotainment system, a navigation system, and/or othervehicle-based computing system. In other embodiments, the mobilenavigation device 110 may instead be embodied as a standalone computingdevice or computing system. For example, in some embodiments, the mobilenavigation device 110 may instead be embodied as a computing deviceunrelated to the vehicle 104. In such embodiments, mobile navigationdevice 110 may be embodied as any type of computing device capable ofperforming the functions described herein (e.g., a server, desktopcomputer, laptop computer, tablet computer, notebook, netbook,Ultrabook™, cellular phone, smartphone, personal digital assistant,mobile Internet device, wearable computing device, consumer electronicdevice, Hybrid device, and/or any other computing/communication device).As illustratively shown in FIG. 2, the mobile navigation device 110includes a processor 112, a memory 116, an input/output (I/O) subsystem118, one or more sensors 120, communication circuitry 122, a datastorage 124, and one or more peripheral devices 126. Of course, themobile navigation device 110 may include other or additional components,such as those commonly found in a computer (e.g., various input/outputdevices), in other embodiments. Additionally, in some embodiments, oneor more of the illustrative components may be incorporated in, orotherwise form a portion of, another component. For example, the memory116, or portions thereof, may be incorporated in the processor 112 insome embodiments.

The processor 112 may be embodied as any type of processor capable ofperforming the functions described herein. For example, in someembodiments, the processor 112 may be embodied as a single coreprocessor, digital signal processor, microcontroller, or other processoror processing/controlling circuit. In other embodiments, such as the oneillustratively shown in FIG. 2, the processor 112 may be embodied as amulti-core processor having multiple processor cores 114. In suchembodiments, each processor core 114 of the processor 112 is capable ofexecuting one or more applications. Additionally, in some embodiments,the processor 112, or a portion thereof, may be embodied as a remotedata processor, virtual processor, computation server, or service. Insuch embodiments, the mobile navigation device 110 may be configured tooffload complex calculations to the remote processor or service forcomputation depending on various criteria (e.g., complexity ofcalculation, location, subscription status, etc.). In some embodiments,some calculations may be performed locally, while others are performedremotely. For example, in some embodiments, the mobile navigation device110 may be embodied as a low-power or low-featured device configured tooffload route calculations and determinations to a remote dataprocessing server or service.

The memory 116 may be embodied as any type of volatile or non-volatilememory or data storage capable of performing the functions describedherein. In operation, the memory 116 may store various data and softwareused during operation of the mobile navigation device 110 such asoperating systems, applications, programs, libraries, and drivers. Thememory 116 is communicatively coupled to the processor 112 via the I/Osubsystem 118, which may be embodied as circuitry and/or components tofacilitate input/output operations with the processor 112, the memory116, and other components of the mobile navigation device 110. Forexample, the I/O subsystem 118 may be embodied as, or otherwise include,memory controller hubs, input/output control hubs, firmware devices,communication links (i.e., point-to-point links, bus links, wires,cables, light guides, printed circuit board traces, etc.) and/or othercomponents and subsystems to facilitate the input/output operations. Insome embodiments, the I/O subsystem 118 may form a portion of asystem-on-a-chip (SoC) and be incorporated, along with the processor112, the memory 116, and other components of the mobile navigationdevice 110, on a single integrated circuit chip.

In the illustrative embodiment, the sensor(s) 120 collect data based onthe physical environment and/or context of the mobile navigation device110. In various embodiments, the sensor(s) 120 may be embodied as, orotherwise include, for example, location sensors, inertial sensors,proximity sensors, optical sensors, light sensors, audio sensors,temperature sensors, motion sensors, piezoelectric sensors, pressuresensors, image sensors, and/or other types of sensors that generate datauseful to the mobile navigation device 110, which may vary depending onthe particular purpose of the mobile navigation device 110. For example,in the illustrative embodiment, the sensor(s) 120 are configured togenerate data indicative of the current location of the vehicle 104and/or the mobile navigation device 110. Additionally or alternatively,the sensor(s) 120 are configured to generate data indicative of thetraffic conditions at the current location of the vehicle 104 and/or themobile navigation device 110.

The communication circuitry 122 of the mobile navigation device 110 maybe embodied as any type of communication circuit, device, or collectionthereof, capable of enabling communications between the mobilenavigation device 110 and other remote devices (e.g., the remote mobilenavigation device(s) 130, the community compute device 140, the cloudservice provider 170, the remote compute device(s) 180, and/or othermember compute devices 106, 162 of the community cloud 102 and/or thepublic cloud 160) via one or more communication networks 190 (e.g.,local area networks, personal area networks, wide area networks,cellular networks, a global network such as the Internet, etc.). Thecommunication circuitry 122 may be configured to use any one or morecommunication technology (e.g., wireless or wired communications) andassociated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.)to effect such communication.

The data storage 124 may be embodied as any type of device or devicesconfigured for short-term or long-term storage of data such as, forexample, memory devices and circuits, memory cards, hard disk drives,solid-state drives, or other data storage devices. For example, the datastorage 124 may be configured to store an operating system to beinitialized and/or executed by the mobile navigation device 110. In someembodiments, portions of the operating system may be copied to thememory 116 during operations for faster processing and/or any otherreason.

In some embodiments, the mobile navigation device 110 may also includeone or more peripheral devices 126. The peripheral devices 126 mayinclude any number of additional peripheral or interface devices, suchas speakers, microphones, additional storage devices, and so forth. Theparticular devices included in the peripheral devices 126 may depend on,for example, the type and/or intended use of the mobile navigationdevice 110 (e.g., whether the mobile navigation device 110 is astand-alone system or incorporated into a larger in-vehicle infotainmentsystem).

The remote mobile navigation device(s) 130 (e.g., the remote mobilenavigation device 130 a and the remote mobile navigation device 130 n)may be embodied as, or form a portion of, an in-vehicle infotainmentsystem, a navigation system, and/or other vehicle-based computing systemassociated with, or otherwise related to, one or more of the remotevehicles 108. In other embodiments, the remote mobile navigationdevice(s) 130 may instead be embodied as standalone computing devices orcomputing systems. For example, in some embodiments, the remote mobilenavigation device(s) 130 may instead be embodied as computing devicesunrelated to the remote vehicle(s) 108. In such embodiments, each of theremote mobile navigation devices 130 may be embodied as any type ofcomputing device capable of performing the functions described herein(e.g., a server, desktop computer, laptop computer, tablet computer,notebook, netbook, Ultrabook™, cellular phone, smartphone, personaldigital assistant, mobile Internet device, wearable computing device,consumer electronic device, Hybrid device, and/or any othercomputing/communication device). As such, the remote mobile navigationdevice(s) 130 may include devices and structures commonly found incomputing devices such as processors, memory devices, communicationcircuitry, and data storages, which are not shown in FIGS. 1-3 forclarity of the description. For example, in the illustrative embodiment,the remote mobile navigation device(s) 130 may include devices andstructures similar to the processor 112, memory 116, input/output (I/O)subsystem 118, sensor(s) 120, communication circuitry 122, data storage124, and peripheral device(s) 126 of the mobile navigation device 110discussed above. In such embodiments, the devices and structures of theremote mobile navigation device(s) 130 may be configured to providefunctionality similar to the functionality provided by the correspondingdevices and structures of the mobile navigation device 110. Of course,the remote mobile navigation device(s) 130 may include other oradditional components, such as those commonly found in a computer (e.g.,various input/output devices), in other embodiments.

The community compute device 140 may be embodied as, or otherwiseinclude, any type of computing device capable of performing thefunctions described herein including, but not limited to a server,desktop computer, laptop computer, tablet computer, notebook, netbook,Ultrabook™, cellular phone, smartphone, personal digital assistant,mobile Internet device, wearable computing device, consumer electronicdevice, smart television, smart appliance, Hybrid device, and/or anyother computing/communication device. As illustratively shown in FIG. 3,the community compute device 140 includes a processor 142, a memory 146,an input/output (I/O) subsystem 148, communication circuitry 150, a datastorage 152, and one or more peripheral devices 154. Of course, thecommunity compute device 140 may include other or additional components,such as those commonly found in a computer (e.g., various input/outputdevices), in other embodiments. Additionally, in some embodiments, oneor more of the illustrative components may be incorporated in, orotherwise form a portion of, another component. For example, the memory146, or portions thereof, may be incorporated in the processor 142 insome embodiments.

The processor 142 may be embodied as any type of processor capable ofperforming the functions described herein. For example, in someembodiments, the processor 142 may be embodied as a single coreprocessor, digital signal processor, microcontroller, or other processoror processing/controlling circuit. In other embodiments, such as the oneillustratively shown in FIG. 3, the processor 142 may be embodied as amulti-core processor having multiple processor cores 144. In suchembodiments, each processor core 144 of the processor 142 is capable ofexecuting one or more applications.

The memory 146 may be embodied as any type of volatile or non-volatilememory or data storage capable of performing the functions describedherein. In operation, the memory 146 may store various data and softwareused during operation of the community compute device 140 such asoperating systems, applications, programs, libraries, and drivers. Thememory 146 is communicatively coupled to the processor 142 via the I/Osubsystem 148, which may be embodied as circuitry and/or components tofacilitate input/output operations with the processor 142, the memory146, and other components of the community compute device 140. Forexample, the I/O subsystem 148 may be embodied as, or otherwise include,memory controller hubs, input/output control hubs, firmware devices,communication links (i.e., point-to-point links, bus links, wires,cables, light guides, printed circuit board traces, etc.) and/or othercomponents and subsystems to facilitate the input/output operations. Insome embodiments, the I/O subsystem 148 may form a portion of asystem-on-a-chip (SoC) and be incorporated, along with the processor142, the memory 146, and other components of the community computedevice 140, on a single integrated circuit chip.

The communication circuitry 150 of the community compute device 140 maybe embodied as any type of communication circuit, device, or collectionthereof, capable of enabling communications between the communitycompute device 140 and other remote devices (e.g., the mobile navigationdevice 110, the remote mobile navigation device(s) 130, the cloudservice provider 170, the remote compute device(s) 180, and/or othermember compute devices 106, 162 of the community cloud 102 and/or thepublic cloud 160) via the one or more communication networks 190 (e.g.,local area networks, personal area networks, wide area networks,cellular networks, a global network such as the Internet, etc.). Thecommunication circuitry 150 may be configured to use any one or morecommunication technology (e.g., wireless or wired communications) andassociated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.)to effect such communication.

The data storage 152 may be embodied as any type of device or devicesconfigured for short-term or long-term storage of data such as, forexample, memory devices and circuits, memory cards, hard disk drives,solid-state drives, or other data storage devices. For example, the datastorage 152 may be configured to store an operating system to beinitialized and/or executed by the community compute device 140. In someembodiments, portions of the operating system may be copied to thememory 146 during operations for faster processing and/or any otherreason.

In some embodiments, the community compute device 140 may also includeone or more peripheral devices 154. The peripheral devices 154 mayinclude any number of additional peripheral or interface devices, suchas speakers, microphones, additional storage devices, and so forth. Theparticular devices included in the peripheral devices 154 may depend on,for example, the type and/or intended use of the community computedevice 140.

The cloud service provider 170 may be embodied as, or otherwise include,any type of computing device (e.g., a server, desktop computer, and/orany other computing/communication device) capable of providingelectronic services (e.g., route navigation, social networking, onlinechatting, e-mail services, online transactions, online purchases,electronic billing statements, electronic bill payment, accountbalances, etc.) over the network(s) 190 to a user and/or a computedevice of the user. As such, the cloud service provider 170 may includedevices and structures commonly found in computing devices such asprocessors, memory devices, communication circuitry, and data storages,which are not shown in FIGS. 1-3 for clarity of the description. In theillustrative embodiment, the cloud service provider 170 may be a membercompute device 162 of the public cloud 160 configured to providenavigation services to the remote compute device(s) 180 and/or othermember compute devices 162 of the public cloud 160. Additionally oralternatively, as discussed below, the cloud service provider 170 may beconfigured to provide navigation services to one or more member computedevices 106 of the community cloud 102. In either case, the cloudservice provider 170 may be configured transmit and/or receive route ornavigation data to/from one or more remote compute devices (e.g., theremote compute device(s) 180, the mobile navigation device 110, theremote mobile navigation device(s) 130, the community compute device140, and/or one or more member compute devices 106, 162 of the communityand public clouds 102, 160). For example, in some embodiments, the cloudservice provider 170 is configured to receive traffic and/or locationdata from a remote compute device 180, generate a navigation route basedon the received traffic and/or location data, and transmit the generatednavigation route to the remote compute device 180 in response.

The remote compute device(s) 180 may be embodied as, or otherwiseinclude, any type of computing device capable of performing thefunctions described herein including, but not limited to a server,desktop computer, laptop computer, tablet computer, notebook, netbook,Ultrabook™, cellular phone, smartphone, personal digital assistant,mobile Internet device, wearable computing device, consumer electronicdevice, smart television, smart appliance, Hybrid device, and/or anyother computing/communication device. As such, the remote computedevice(s) 180 may include devices and structures commonly found incomputing devices such as processors, memory devices, communicationcircuitry, and data storages, which are not shown in FIGS. 1-3 forclarity of the description. In some embodiments, the remote computedevice(s) 180 may be member compute devices 162 of the public cloud 160.In such embodiments, the remote compute device(s) 180 may be configuredto transmit and/or receive route navigation data to/from the cloudservice provider 170.

Referring now to FIG. 4, in use, the mobile navigation device 110establishes an environment 400 during operation. The illustrativeenvironment 400 includes a route monitoring module 402, a routedetermination module 406, and a privacy management module 408. In someembodiments, the route monitoring module 402 includes a route processingdetermination module 404. Each of the modules, logic, and othercomponents of the environment 400 may be embodied as hardware, software,firmware, or a combination thereof. For example, each of the modules,logic and other components of the environment 400 may form a portion of,or otherwise be established by, the processor 112 or other hardwarecomponents of the mobile navigation device 110. It should be appreciatedthat the mobile navigation device 110 may include other components,sub-components, modules, and devices commonly found in a computingdevice, which are not illustrated in FIG. 4 for clarity of thedescription. As discussed above, the remote mobile navigation device(s)130 of the remote vehicles 108 may include devices and structuressimilar to the devices and structures of the mobile navigation device110. As such, in use, the remote mobile navigation device(s) 130 mayalso establish the environment 400 during operation. However, thefollowing discussion of that illustrative environment 400 is describedwith specific reference to the mobile navigation device 110 for clarityof the description.

The route monitoring module 402 is configured to determine whether areference traffic event occurs within a segment (e.g., a portion,subset, etc.) of a current route of the vehicle 104 based on sensor datagenerated by the sensor(s) 120. In some embodiments, the sensor data mayinclude location data (e.g., latitude, longitude, elevation, city,state, country, address, etc.) indicative of a current location of thevehicle 104 and/or the mobile navigation device 110. Additionally oralternatively, the sensor data may include traffic data indicative of acurrent traffic condition (e.g., a current traffic flow, current weatherconditions, a roadway obstruction, a roadway hazard, a traffic accident,etc.) sensed, measured, and/or identified at the current location of thevehicle 104 and/or the mobile navigation device 110. The referencetraffic event may be embodied as any one or a combination of a referenceamount of traffic congestion (e.g., a threshold volume of traffic,etc.), a reference type of traffic accident (e.g., a fender bender, anaccident blocking one or more lanes of traffic, etc.), a referenceamount of roadway construction (e.g., a threshold distance of roadwayunder construction, a threshold number of lanes reduced in aconstruction zone, etc.), a reference roadway obstruction (e.g., apredefined type of roadway obstruction, a threshold number of lanesreduced because of a roadway obstruction, etc.), or a reference roadwayhazard (e.g., a predefined roadway condition such as icy or wetpavement, etc.).

The route monitoring module 402 is also configured to determine whetherto generate an alternate route to avoid a reference traffic eventoccurring in a segment of a current route of the vehicle 104 based onsensor data received from a remote compute device (e.g., the remotemobile navigation device(s) 130, the community compute device 140,and/or any other member compute device 106 of the community cloud 102).For example, in some embodiments, sensor data may be received from aremote mobile navigation device 130 (e.g., the remote mobile navigationdevice 130 a) indicative of a reference traffic event occurring in asegment of a current route of the remote vehicle 108. In suchembodiments, the mobile navigation device 110 may determine whether togenerate an alternate route to avoid the occurrence of the referencetraffic event in one or more segments of the current route of thevehicle 104 that correspond to, or are otherwise similar to, the segmentof the current route of the remote vehicle 108.

Additionally, in some embodiments, the route monitoring module 402 maybe configured to determine whether the generation of an alternate routeto avoid a reference traffic event occurring in a segment of a currentroute of the vehicle 104 should be performed by the mobile navigationdevice 110 or another member compute device 106 of the community cloud102 (e.g., the community compute device 140). To do so, the routemonitoring module 402 may include the route processing determinationmodule 404. The route processing determination module 404 may beconfigured to make such determinations based on, or otherwise as afunction of, the amount of processing power required to generate thealternate route from the sensor data received from the remote computedevice (e.g., the remote mobile navigation device(s) 130, the communitycompute device 140, and/or any other member compute device 106 of thecommunity cloud 102). Additionally or alternatively, the routeprocessing determination module 404 may be configured to make suchdeterminations based on, or otherwise as a function of, an amount ofremaining battery charge associated with the mobile navigation device110. Of course, the route processing determination module 404 may beconfigured to use any other criteria or condition to determine whetherthe alternate route should be generated by the mobile navigation device110 or another member compute device 106 of the community cloud 102.Additionally, in some embodiments, the route processing determinationmodule 404 may be configured to offload the route processingdetermination, or a portion thereof, to a remote data processing serveror service as discussed above.

The route determination module 406 is configured to transmit routenavigation data to one or more member compute devices 106 of thecommunity cloud 102. For example, in some embodiments, the routedetermination module 406 is configured to transmit route update data toa remote mobile navigation device 130 (e.g., the remote mobilenavigation device 130 a) in response to determining or otherwiseidentifying the occurrence of a reference traffic event in a segment ofthe current route of the vehicle 104. Upon receipt, the route updatedata may be used by the remote mobile navigation device 130 to updateone or more segments of a current navigation route (e.g., an existingroute, a commonly traveled route, a future route, etc.) associated withthe remote vehicle 108 that correspond to the segment of the currentroute of the vehicle 104 within which the reference traffic event isdetermined to be occurring. In some embodiments, the route update dataincludes the sensor data generated by the sensor(s) 120 of the mobilenavigation device 110.

In some embodiments, the route determination module 406 is configured togenerate an alternate route of the remote vehicle 108 in response todetermining the occurrence of a reference traffic event in a segment ofthe current route of the vehicle 104. The alternate route may begenerated based on the sensor data generated by the sensor(s) 120. Insuch embodiments, the route update data transmitted to the remote mobilenavigation device 130 may include the alternate route generated by theroute determination module 406. As such, the remote mobile navigationdevice 130 may use the alternate route generated by the routedetermination module 406 to update a current route (e.g., an existingroute, a commonly traveled route, a future route, etc.) of the remotevehicle 108 to avoid the reference traffic event.

Additionally or alternatively, the route determination module 406 mayalso be configured to determine and/or select an alternate route out ofa plurality of previously generated alternate routes that may be used bythe remote mobile navigation device 130 of the remote vehicle 108 toavoid the occurrence of the reference traffic event. To do so, the routedetermination module 406 may determine and/or select the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring. Of course, itshould be appreciated that the route determination module 406 may useany process or metric for determining and/or selecting the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring. To facilitatenotifying the remote mobile navigation device 130 of the particularalternate route selected, each of the plurality of previously generatedalternate routes may be associated with a different route identifier. Assuch, in response to determining and/or selecting the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring, the routedetermination module 406 is configured to determine the route identifierassociated therewith. In embodiments in which the route determinationmodule 406 determines and/or selects the particular alternate route bestsuited to avoid the location or route segments within which thereference traffic event is occurring, the route update data transmittedto the remote mobile navigation device 130 may include the correspondingroute identifier. In some embodiments, each of the plurality ofpreviously generated alternate routes and the corresponding unique routeidentifiers may be generated and received from the remote mobilenavigation device 130.

In some embodiments, the route determination module 406 may also beconfigured to generate an alternate route for the vehicle 104 to avoidand/or reroute around the segment of the current route of the vehicle104 in which the reference traffic event is determined to have occurred.In such embodiments, the route determination module 406 may generate thealternate route for the vehicle 104 based on the sensor data generatedby the sensor(s) 120. As such, it should be appreciated that in additionto generating route update data to transmit to the remote mobilenavigation device 130 for avoidance of the reference traffic event, theroute determination module 406 may also generate an alternate route forthe vehicle 104 for avoidance of, or rerouting around, the referencetraffic event.

In some embodiments, the route determination module 406 may also beconfigured to receive a request from the remote mobile navigation device130 for route data associated with a future route (e.g., an upcomingroute, etc.) of the remote vehicle 108. The requested route data may beembodied as historical sensor data generated by the sensor(s) 120 duringa previous navigation route of the vehicle 104. In such embodiments, theroute determination module 406 may transmit the requested route data tothe remote mobile navigation device 130. Additionally or alternatively,the route determination module 406 may also be configured to transmitthe sensor data generated by the sensor(s) 120 to the community computedevice 140 and/or another member compute device 106 of the communitycloud 102 for analysis and processing (e.g., reference traffic eventoccurrence determination, alternate route determination, alternate routegeneration, etc.).

The route determination module 406 is also configured to update thecurrent route of the vehicle 104 based on route update data receivedfrom a member compute device 106 of the community cloud 102. Forexample, in some embodiments, the route determination module 406 isconfigured to receive route update data from a remote mobile navigationdevice 130 (e.g., the remote mobile navigation device 130 a) and/or thecommunity compute device 140. In such embodiments, the received routeupdate data may include sensor data generated by one or more sensors ofthe remote mobile navigation device 130, an alternate route generated bythe remote mobile navigation device 130 and/or the community computedevice 140, and/or a route identifier associated with a previouslygenerated alternate route selected by the remote mobile navigationdevice 130 and/or the community compute device 140. In some embodiments,the route determination module 406 may use the received route updatedata to avoid a reference traffic event occurrence within a segment ofthe current route of the vehicle 104. In embodiments in which the routeupdate data includes a route identifier associated with a previouslygenerated alternate route selected by the remote mobile navigationdevice 130 and/or the community compute device 140, the routedetermination module 406 may be configured to transmit the plurality ofpreviously generated alternate routes and the corresponding identifiersto the remote mobile navigation device 130 and/or the community computedevice 140. Additionally, in some embodiments, the route determinationmodule 406 may receive the route update data from the remote mobilenavigation device 130 and/or the community compute device 140 inresponse to the remote mobile navigation device 130 and/or the communitycompute device 140 determining, based on data received from the remotemobile navigation device 130, that the reference traffic event isoccurring in one or more segments of the current route of the vehicle104. Additionally or alternatively, the route determination module 406may receive the route update data from the remote mobile navigationdevice 130 and/or the community compute device 140 in response to arequest transmitted to the remote mobile navigation device 130 and/orthe community compute device 140.

In some embodiments, the route determination module 406 may also beconfigured to transmit a request to a remote mobile navigation device130 (e.g., the remote mobile navigation device 130 a) and/or thecommunity compute device 140 for route data associated with a futureroute (e.g., an upcoming route, etc.) of the vehicle 104. The requestedroute data may be embodied as historical sensor data generated by theone or more sensors of the remote mobile navigation device 130 during aprevious navigation route of the remote vehicle 108. Additionally oralternatively, in some embodiments, the route determination module 406may also be configured to transmit a request to the cloud serviceprovider 170 of the public cloud 160 for route data associated with afuture route (e.g., an upcoming route, etc.) of the vehicle 104. In suchembodiments, the requested route data may be embodied as historicalsensor data generated by the one or more sensors of the remote computedevices 180 and/or other member compute devices 162 of the public cloud160 during previous navigation routes of other remote vehicles. Itshould be appreciated, however, that transmitting and/or receiving routedata (e.g., sensor data, route update data, etc.) to/from member computedevices 162 of the public cloud 160 requires a user of the mobilenavigation device 110 to sacrifice a portion of their privacy.

Additionally or alternatively, the route determination module 406 mayalso be configured to update the current route of the vehicle 104. Asdiscussed, in some embodiments, the route determination module 406 isconfigured to generate an alternate route for the vehicle 104 based onthe sensor data generated by the sensor(s) 120. In such embodiments, theroute determination module 406 may be configured to update the currentroute of the vehicle 104 based on the locally-generated alternate route.

The privacy management module 408 is configured to controlcommunications and/or interactions between the mobile navigation device110 and one or more remote compute devices (e.g., the remote mobilenavigation device(s) 130, the community compute device 140, the cloudservice provider 170, the remote compute device(s) 180, and/or any othermember compute devices 106, 162 of the community and public clouds 102,160). For example, in some embodiments, the privacy management module408 is configured to prevent the transmission and/or reception of routeupdate data to/from member compute devices 162 of the public cloud 160.In that way, the privacy of the member compute devices 106 of thecommunity cloud 102 may be maintained.

Referring now to FIG. 5, in use, the community compute device 140establishes an environment 500 during operation. The illustrativeenvironment 500 includes a community route monitoring module 502, acommunity route determination module 504, and a community privacymanagement module 506. Each of the modules, logic, and other componentsof the environment 500 may be embodied as hardware, software, firmware,or a combination thereof. For example, each of the modules, logic andother components of the environment 500 may form a portion of, orotherwise be established by, the processor 142 or other hardwarecomponents of the community compute device 140. It should be appreciatedthat the community compute device 140 may include other components,sub-components, modules, and devices commonly found in a computingdevice, which are not illustrated in FIG. 5 for clarity of thedescription.

The community route monitoring module 502 is configured to receivesensor data from member compute devices 106 of the community cloud 102.For example, in some embodiments, the community route monitoring module502 is configured to receive sensor data from the mobile navigationdevice 110 of the vehicle 104. The sensor data may be generated by thesensor(s) 120 of the mobile navigation device 110 during a current routeof the vehicle 104. In some embodiments, the sensor data may includelocation data (e.g., latitude, longitude, elevation, city, state,country, address, etc.) indicative of a current location of the vehicle104 and/or the mobile navigation device 110. Additionally oralternatively, the sensor data may include traffic data indicative of acurrent traffic condition (e.g., a current traffic flow, current weatherconditions, a roadway obstruction, a roadway hazard, a traffic accident,etc.) sensed, measured, and/or identified at the current location of thevehicle 104 and/or the mobile navigation device 110. It should beappreciated, however, that the sensor data may be received from any oneor more of the remote mobile navigation devices 130 instead.

Additionally, the community route monitoring module 502 is configured todetermine whether a reference traffic event occurs within a segment(e.g., a portion, subset, etc.) of a current route of a vehicle (e.g.,the vehicle 104 or one of the remote vehicles 108) based on the receivedsensor data. For example, in some embodiments, the community routemonitoring module 502 is configured to determine whether a referencetraffic event occurs within a segment of the current route of thevehicle 104 based on sensor data received from the mobile navigationdevice 110. The reference traffic event may be embodied as any one or acombination of a reference amount of traffic congestion (e.g., athreshold volume of traffic, etc.), a reference type of traffic accident(e.g., a fender bender, an accident blocking one or more lanes oftraffic, etc.), a reference amount of roadway construction (e.g., athreshold distance of roadway under construction, a threshold number oflanes reduced in a construction zone, etc.), a reference roadwayobstruction (e.g., a predefined type of roadway obstruction, a thresholdnumber of lanes reduced because of a roadway obstruction, etc.), or areference roadway hazard (e.g., a predefined roadway condition such asicy or wet pavement, etc.).

The community route determination module 504 is configured to transmitroute navigation data to one or more member compute devices 106 of thecommunity cloud 102. For example, in some embodiments, the communityroute determination module 504 is configured to transmit route updatedata to the mobile navigation device 110 of the vehicle 104 in responseto determining or otherwise identifying the occurrence of a referencetraffic event in a segment of the current route of the remote vehicle108. Upon receipt, the route update data may be used by the mobilenavigation device 110 to update one or more segments of a currentnavigation route (e.g., an existing route, a commonly traveled route, afuture route, etc.) associated with the vehicle 104 that correspond tothe segment of the current route of the remote vehicle 108 within whichthe reference traffic event is determined to be occurring. In someembodiments, the route update data includes the sensor data generated bythe sensor(s) of the remote mobile navigation device 130.

In some embodiments, the community route determination module 504 isconfigured to generate an alternate route in response to determining theoccurrence of a reference traffic event in a segment of the currentroute of the remote vehicle 108. The alternate route may be generatedbased on the sensor data generated by the sensor(s) of the remote mobilenavigation device 130. In such embodiments, the route update datatransmitted to the mobile navigation device 110 may include thealternate route generated by the community route determination module504. As such, the mobile navigation device 110 may use the alternateroute generated by the community route determination module 504 toupdate a current route (e.g., an existing route, a commonly traveledroute, a future route, etc.) of the vehicle 104 to avoid the referencetraffic event.

Additionally or alternatively, the community route determination module504 may also be configured to determine and/or select an alternate routeout of a plurality of previously generated alternate routes that may beused by the mobile navigation device 110 of the vehicle 104 to avoid theoccurrence of the reference traffic event. To do so, the community routedetermination module 504 may determine and/or select the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring. Of course, itshould be appreciated that the community route determination module 504may use any process or metric for determining and/or selecting theparticular alternate route best suited to avoid the location or routesegments within which the reference traffic event is occurring. Tofacilitate notifying the mobile navigation device 110 of the particularalternate route selected, each of the plurality of previously generatedalternate routes may be associated with a different route identifier. Assuch, in response to determining and/or selecting the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring, the communityroute determination module 504 is configured to determine the routeidentifier associated therewith. In embodiments in which the communityroute determination module 504 determines and/or selects the particularalternate route best suited to avoid the location or route segmentswithin which the reference traffic event is occurring, the route updatedata transmitted to the mobile navigation device 110 may include thecorresponding route identifier. In some embodiments, each of theplurality of previously generated alternate routes and the correspondingunique route identifiers may be generated and received from the mobilenavigation device 110.

In some embodiments, the community route determination module 504 mayalso be configured to receive a request from the mobile navigationdevice 110 and/or one of the remote mobile navigation device(s) 130 forroute data associated with a future route (e.g., an upcoming route,etc.) of the vehicle 104 or one of the remote vehicle(s) 108. Therequested route data may be embodied as historical sensor data generatedby the sensor(s) of the mobile navigation device 110 and/or the remotemobile navigation device(s) 130 during previous navigation routes of thevehicle(s) 104, 108. In such embodiments, the community routedetermination module 504 may transmit the route data to the mobilenavigation device 110 and/or the remote mobile navigation device 130that requested the data. Additionally or alternatively, the communityroute determination module 504 may also be configured to transmit thesensor data generated by the sensor(s) of the mobile navigation device110 and/or the remote mobile navigation device(s) 130 to one or more ofthe member compute devices 106 of the community cloud 102 for analysisand processing (e.g., reference traffic event occurrence determination,alternate route determination, alternate route generation, etc.).

The community privacy management module 506 is configured to controlcommunications and/or interactions between the community compute device140 and one or more remote compute devices (e.g., the mobile navigationdevice 110, the remote mobile navigation device(s) 130, the cloudservice provider 170, the remote compute device(s) 180, and/or any othermember compute devices 106, 162 of the community and public clouds 102,160). For example, in some embodiments, the community privacy managementmodule 506 is configured to prevent the transmission and/or reception ofroute update data to/from member compute devices 162 of the public cloud160. In that way, the privacy of the member compute devices 106 of thecommunity cloud 102 may be maintained.

Referring now to FIG. 6, the mobile navigation device 110 may execute amethod 600 for sharing route navigation data in the community cloud 102.The method 600 begins with block 602 in which the sensor(s) 120 of themobile navigation device 110 generate sensor data associated with acurrent route of the vehicle 104. In some embodiments, the sensor datagenerated by the sensor(s) 120 of the mobile navigation device 110includes location data indicative of a current location of the vehicle104 and/or the mobile navigation device 110. For example, in someembodiments, the sensor(s) 120 of the mobile navigation device 110generate location data indicative of, but not limited to, the latitude,longitude, elevation, city, state, country, and/or address at which thevehicle 104 and/or the mobile navigation device 110 is currentlylocated. Additionally or alternatively, the sensor data generated by thesensor(s) 120 of the mobile navigation device 110 includes traffic dataindicative of a current traffic condition sensed, measured, and/oridentified at the current location of the vehicle 104 and/or the mobilenavigation device 110. For example, such traffic data may be indicativeof the current traffic flow measured at the current location of thevehicle 104, the current weather conditions identified at the currentlocation of the vehicle 104, a roadway obstruction identified at thecurrent location of the vehicle 104, or a roadway hazard identified atthe current location of the vehicle 104. In another example, the trafficdata may be indicative of a traffic accident identified at the currentlocation of the vehicle 104 via an analysis of one or more imagescaptured at the current location of the vehicle 104. Of course, anyother type of traffic data may be sensed, measured, and/or identified bythe sensor(s) 120 of the mobile navigation device 110 in otherembodiments.

In block 604, the mobile navigation device 110 determines whether areference traffic event occurs within a segment (e.g., a portion,subset, etc.) of the current route of the vehicle 104 based on thesensor data generated by the sensor(s) 120. The reference traffic eventmay be embodied as any one or a combination of a reference amount oftraffic congestion (e.g., a threshold volume of traffic, etc.), areference type of traffic accident (e.g., a fender bender, an accidentblocking one or more lanes of traffic, etc.), a reference amount ofroadway construction (e.g., a threshold distance of roadway underconstruction, a threshold number of lanes reduced in a constructionzone, etc.), a reference roadway obstruction (e.g., a predefined type ofroadway obstruction, a threshold number of lanes reduced because of aroadway obstruction, etc.), or a reference roadway hazard (e.g., apredefined roadway condition such as icy or wet pavement, etc.). Themethod 600 then advances to decision block 606. If, in decision block606, the mobile navigation device 110 determines that a referencetraffic event occurs within a segment of the current route of thevehicle 104, the method 600 advances to block 608. If, however, themobile navigation device 110 instead determines in decision block 606that a reference traffic event does not occur within a segment of thecurrent route of the vehicle 104, the method 600 loops back to block 602and the sensor(s) 120 of the mobile navigation device 110 continuegenerating sensor data.

In some embodiments, the segment of the current route of the vehicle 104in which the mobile navigation device 110 determines that the referencetraffic event occurs corresponds to, or is otherwise similar to, one ormore segments of a navigation route (e.g., an existing route, a commonlytraveled route, a future route, etc.) associated with the remote vehicle108. As such, in block 608, the mobile navigation device 110 transmitsroute update data to the remote mobile navigation device 130 of theremote vehicle 108 in response to determining that a reference trafficevent occurs within the segment of the current route of the vehicle 104.The route update data may be used by the remote mobile navigation device130 to update corresponding or similar segments of navigation route(e.g., the existing route, commonly traveled route, future route, etc.)of the remote vehicle 108 to avoid the occurrence of the referencetraffic event. In some embodiments, the route update data includes thesensor data generated by the sensor(s) 120 of the mobile navigationdevice 110. In such embodiments, the route update data may be analyzedby the remote mobile navigation device 130 to facilitate avoidance ofthe reference traffic event occurrence by the remote vehicle 108.

Additionally or alternatively, in some embodiments, the route updatedata transmitted by the mobile navigation device 110 includes analternate route for use by the remote mobile navigation device 130 toavoid the corresponding or similar segments of the navigation route ofthe remote vehicle 108 in which the reference traffic event isdetermined to have occurred. In such embodiments, in block 610, themobile navigation device 110 generates the alternate route for theremote vehicle 108 based on the sensor data generated by the sensor(s)120 and the determined occurrence of the reference traffic event. Inother embodiments, the route update data transmitted by the mobilenavigation device 110 may instead include a route identifier thatidentifies or is otherwise indicative of a previously generatedalternate route for avoiding the occurrence of the reference trafficevent. In such embodiments, in block 612, the mobile navigation device110 determines and/or selects an alternate route of a plurality ofpreviously generated alternate routes capable of avoiding the occurrenceof the reference traffic event. Each previously generated alternateroute is associated with a different route identifier. In response todetermining a particular previously generated alternate route thatavoids the occurrence of the reference traffic event, the mobilenavigation device 110 transmits the associated route identifier to theremote mobile navigation device 130. The remote mobile navigation device130 may thereafter use the route identifier to retrieve thecorresponding previously generated alternate route from local memory. Inembodiments in which the route update data transmitted by the mobilenavigation device 110 includes a route identifier, the previouslygenerated alternate routes and the associated route identifiers may bereceived from the remote mobile navigation device 130 periodically or inresponse to a request by the mobile navigation device 110.

In some embodiments, in block 614, the mobile navigation device 110 mayalso generate an alternate route to avoid the segment of the currentroute of the vehicle 104 in which the reference traffic event isdetermined to have occurred. In such embodiments, the mobile navigationdevice 110 may generate the alternate route for the vehicle 104 based onthe sensor data generated by the sensor(s) 120. As such, it should beappreciated that in addition to generating route update data to transmitto the remote mobile navigation device 130 for avoidance of thereference traffic event, the mobile navigation device 110 may alsogenerate an alternate route for the vehicle 104 for avoidance of, orrerouting around, the reference traffic event.

Referring now to FIG. 7, the community compute device 140 may execute amethod 700 for sharing route navigation data in the community cloud 102.The method 700 begins with decision block 702 in which the communitycompute device 140 determines whether sensor data is received from themobile navigation device 110 of the vehicle 104. In some embodiments,the sensor data includes location data (e.g., latitude, longitude,elevation, city, state, country, address, etc.) indicative of a currentlocation of the vehicle 104 and/or the mobile navigation device 110.Additionally or alternatively, the sensor data includes traffic dataindicative of a current traffic condition (e.g., a current traffic flow,current weather conditions, a roadway obstruction, a roadway hazard, atraffic accident, etc.) sensed, measured, and/or identified at thecurrent location of the vehicle 104 and/or the mobile navigation device110. If, in decision block 702, the community compute device 140determines that the sensor data is received from the mobile navigationdevice 110, the method 700 advances to block 704. If, however, thecommunity compute device 140 instead determines in decision block 702that sensor data is not received from the mobile navigation device 110,the method 700 loops back to decision block 702 and the communitycompute device 140 monitors for receipt of sensor data from the mobilenavigation device 110.

In block 704, the community compute device 140 determines whether areference traffic event occurs within a segment (e.g., a portion,subset, etc.) of the current route of the vehicle 104 based on thesensor data received from the mobile navigation device 110. Thereference traffic event may be embodied as any one or a combination of areference amount of traffic congestion (e.g., a threshold volume oftraffic, etc.), a reference type of traffic accident (e.g., a fenderbender, an accident blocking one or more lanes of traffic, etc.), areference amount of roadway construction (e.g., a threshold distance ofroadway under construction, a threshold number of lanes reduced in aconstruction zone, etc.), a reference roadway obstruction (e.g., apredefined type of roadway obstruction, a threshold number of lanesreduced because of a roadway obstruction, etc.), or a reference roadwayhazard (e.g., a predefined roadway condition such as icy or wetpavement, etc.). The method 700 then advances to decision block 706. If,in decision block 706, the community compute device 140 determines thata reference traffic event occurs within a segment of the current routeof the vehicle 104, the method 700 advances to block 708. If, however,the community compute device 140 instead determines in decision block706 that a reference traffic event does not occur within a segment ofthe current route of the vehicle 104, the method 700 loops back todecision block 702 and the community compute device 140 monitors forreceipt of new sensor data from the mobile navigation device 110.

In some embodiments, the segment of the current route of the vehicle 104in which the community compute device 140 determines that the referencetraffic event has occurred corresponds to, or is otherwise similar to,one or more segments of a navigation route (e.g., an existing route, acommonly traveled route, a future route, etc.) associated with theremote vehicle 108. As such, in block 708, the community compute device140 transmits route update data to the remote mobile navigation device130 of the remote vehicle 108 in response to determining that areference traffic event occurs within the segment of the current routeof the vehicle 104. The route update data may be used by the remotemobile navigation device 130 to update corresponding or similar segmentsof navigation route (e.g., the existing route, commonly traveled route,future route, etc.) of the remote vehicle 108 to avoid the occurrence ofthe reference traffic event. In some embodiments, the route update dataincludes the sensor data received from the mobile navigation device 110.In such embodiments, the route update data may be analyzed by the remotemobile navigation device 130 to facilitate avoidance of the referencetraffic event occurrence by the remote vehicle 108.

Additionally or alternatively, in some embodiments, the route updatedata transmitted by the community compute device 140 includes analternate route for use by the remote mobile navigation device 130 toavoid the corresponding or similar segments of the navigation route ofthe remote vehicle 108 in which the reference traffic event isdetermined to have occurred. In such embodiments, in block 710, thecommunity compute device 140 generates the alternate route for theremote vehicle 108 based on the received sensor data and the determinedoccurrence of the reference traffic event. In other embodiments, theroute update data transmitted by the community compute device 140 mayinstead include a route identifier that identifies or is otherwiseindicative of a previously generated alternate route for avoiding theoccurrence of the reference traffic event. In such embodiments, in block712, the community compute device 140 determines and/or selects analternate route of a plurality of previously generated alternate routescapable of avoiding the occurrence of the reference traffic event. Eachpreviously generated alternate route is associated with a differentroute identifier. In response to determining a particular previouslygenerated alternate route that avoids the occurrence of the referencetraffic event, the community compute device 140 transmits the associatedroute identifier to the remote mobile navigation device 130. The remotemobile navigation device 130 may thereafter use the route identifier toretrieve the corresponding previously generated alternate route fromlocal memory. In embodiments in which the route update data transmittedby the community compute device 140 includes a route identifier, thepreviously generated alternate routes and the associated routeidentifiers may be received from the remote mobile navigation device 130periodically or in response to a request by the community compute device140.

Referring now to FIG. 8, the mobile navigation device 110 of the vehicle104 may execute a method 800 for updating a navigation route based onnavigation data shared in the community cloud 102. The method 800 beginswith decision block 802 in which the mobile navigation device 110determines whether route update data is received from a member computedevice 106 (e.g., the remote mobile navigation device(s) 130, thecommunity compute device 140, etc.) of the community cloud 102. In someembodiments, the route update data is associated with the occurrence ofa reference traffic event within at least one segment of a route of aremote vehicle 108 that corresponds to, or is otherwise similar to, oneor more segments of a current route of the vehicle 104. In someembodiments, the route update data includes sensor data received fromthe remote mobile navigation device 130 of the remote vehicle 108.Additionally or alternatively, the route update data may be embodied asan alternate route generated by a member compute device 106 of thecommunity cloud 102 to facilitate avoidance of the reference trafficevent occurrence by the vehicle 104. In other embodiments, the routeupdate data may be embodied as a route identifier that identifies or isotherwise indicative of a previously generated alternate route foravoiding the occurrence of the reference traffic event. If, in decisionblock 802, the mobile navigation device 110 determines that route updatedata is received from a member compute device 106 of the community cloud102, the method 800 advances to block 804. If, however, the mobilenavigation device 110 instead determines in decision block 802 thatroute update data is not received from a member compute device 106 ofthe community cloud 102, the method 800 loops back to decision block 802and the mobile navigation device 110 monitors for receipt of routeupdate data from a member compute device 106 of the community cloud 102.

In block 804, the mobile navigation device 110 updates the current routeof the vehicle 104 to avoid the occurrence of the reference trafficevent based on the received route update data. To do so, in someembodiments, the mobile navigation device 110 generates, in block 806,an alternate route to avoid the occurrence of the reference trafficevent in one or more segments of the current route of the vehicle 104based on the route update data received from the member compute device106 (e.g., the remote mobile navigation device 130, the communitycompute device 140, etc.) of the community cloud 102. For example, insome embodiments, the mobile navigation device 110 may generate thealternate route based on an analysis of the sensor data received fromthe remote mobile navigation device 130. In other embodiments, in block808, the mobile navigation device 110 may use the received route updatedata to determine an alternate route of a plurality of previouslygenerated alternate routes capable of avoiding the occurrence of thereference traffic event. In such embodiments, the route update datareceived from the member compute device 106 of the community cloud 102may include a route identifier that identifies or is otherwiseindicative of a particular previously generated alternate route capableof avoiding the occurrence of the reference traffic event. As such, inresponse to receiving route update data that includes a routeidentifier, the mobile navigation device 110 may use the routeidentifier to retrieve the corresponding previously generated alternateroute corresponding from local memory. In some embodiments, the mobilecomputing device 110 may transmit the plurality of previously generatedalternate routes and the associated route identifiers to one or more ofthe member compute devices 106 of the community cloud 102 periodicallyor in response to a request from a member compute device 106 of thecommunity cloud 102.

EXAMPLES

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including a sensorto generate sensor data associated with a current route of the vehicle,wherein at least a segment of the current route of the vehiclecorresponds to one or more segments of an existing route of a remotevehicle; a route monitoring module to determine, based on the generatedsensor data, an occurrence of a reference traffic event within thesegment of the current route of the vehicle; and a route determinationmodule to transmit route update data to a remote mobile navigationdevice of the remote vehicle in response to a determination of theoccurrence of the reference traffic event within the segment of thecurrent route.

Example 2 includes the subject matter of Example 1, and wherein theroute determination module is further to generate, in response to adetermination of the occurrence of the reference traffic event withinthe segment of the current route, an alternate route for the remotevehicle to avoid the one or more segments of the existing route of theremote vehicle that correspond to the segment of the current route; andwherein to transmit the route update data includes to transmit thealternate route to the remote mobile navigation device of the remotevehicle.

Example 3 includes the subject matter of any of Examples 1 and 2, andwherein the route determination module is further to (i) determine, inresponse to a determination of the occurrence of the reference trafficevent within the segment of the current route, an alternate route of aplurality of alternate routes for the remote vehicle to avoid the one ormore segments of the existing route of the remote vehicle thatcorrespond to the segment of the current route, wherein each alternateroute is associated with a route identifier that identifies eachalternate route within the plurality of alternate routes and (ii)determine the route identifier associated with the alternate routedetermined for the remote vehicle; and wherein to transmit the routeupdate data includes to transmit, to the remote mobile navigation deviceof the remote vehicle, the route identifier associated with thealternate route determined for the remote vehicle.

Example 4 includes the subject matter of any of Examples 1-3, andwherein the route determination module is further to receive, from theremote mobile navigation device of the remote vehicle, one or more ofthe plurality of alternate routes and the route identifier associatedwith each of the one or more of the plurality of alternate routesreceived; and wherein to determine the alternate route and theassociated route identifier for the remote vehicle includes to determinethe alternate route and the associated route identifier for the remotevehicle from the one or more alternate routes of the plurality ofalternate routes received from the remote mobile navigation device ofthe remote vehicle.

Example 5 includes the subject matter of any of Examples 1-4, andwherein the route determination module is further to generate, inresponse to a determination of the occurrence of the reference trafficevent within the segment of the current route of the vehicle, analternate route for the vehicle to avoid the segment of the currentroute of the vehicle.

Example 6 includes the subject matter of any of Examples 1-5, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 7 includes the subject matter of any of Examples 1-6, andwherein to generate the sensor data associated with the current route ofthe vehicle includes to generate location data indicative of a currentlocation of the vehicle.

Example 8 includes the subject matter of any of Examples 1-7, andwherein to generate the sensor data associated with the current route ofthe vehicle further includes to generate traffic data indicative of acurrent traffic condition at the current location of the vehicle.

Example 9 includes the subject matter of any of Examples 1-8, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the vehicle, current weatherconditions at the current location of the vehicle, a traffic accident atthe current location of the vehicle, a roadway obstruction at thecurrent location of the vehicle, or a roadway hazard at the currentlocation of the vehicle.

Example 10 includes the subject matter of any of Examples 1-9, andwherein to generate the traffic data indicative of the current trafficcondition includes to generate traffic data indicative of a trafficaccident at the current location of the vehicle based on an analysis ofone or more images captured at the current location of the vehicle.

Example 11 includes the subject matter of any of Examples 1-10, andwherein the route determination module is further to (i) receive, fromthe remote mobile navigation device of the remote vehicle, a request forroute data associated with a future route of the remote vehicle and (ii)transmit, to the remote mobile navigation device, the requested routedata based on historical sensor data generated by the mobile navigationdevice for a past route of the vehicle.

Example 12 includes the subject matter of any of Examples 1-11, andwherein the mobile navigation device of the vehicle and the remotemobile navigation device are each member compute devices of a communitycloud; and wherein to transmit the route update data to the remotemobile navigation device includes to transmit the route update data tothe remote mobile navigation device of the community cloud.

Example 13 includes the subject matter of any of Examples 1-12, andfurther including a privacy management module to prevent transmission ofthe route update data to member compute devices of a public cloud,wherein the public cloud is different from the community cloud.

Example 14 includes the subject matter of any of Examples 1-13, andwherein the route determination module is further to transmit the sensordata to a community compute device of the community cloud for analysis.

Example 15 includes a method for sharing route navigation data, themethod including generating, by a mobile navigation device of a vehicle,sensor data associated with a current route of the vehicle, wherein atleast a segment of the current route of the vehicle corresponds to oneor more segments of an existing route of a remote vehicle; determining,by the mobile navigation device and based on the generated sensor data,an occurrence of a reference traffic event within the segment of thecurrent route of the vehicle; and transmitting, by the mobile navigationdevice, route update data to a remote mobile navigation device of theremote vehicle in response to a determination of the occurrence of thereference traffic event within the segment of the current route.

Example 16 includes the subject matter of Example 15, and furtherincluding generating, by the mobile navigation device and in response toa determination of the occurrence of the reference traffic event withinthe segment of the current route, an alternate route for the remotevehicle to avoid the one or more segments of the existing route of theremote vehicle that correspond to the segment of the current route; andwherein transmitting the route update data includes transmitting analternate route to the remote mobile navigation device of the remotevehicle.

Example 17 includes the subject matter of any of Examples 15 and 16, andfurther including determining, by the mobile navigation device and inresponse to a determination of the occurrence of the reference trafficevent within the segment of the current route, an alternate route of aplurality of alternate routes for the remote vehicle to avoid the one ormore segments of the existing route of the remote vehicle thatcorrespond to the segment of the current route, wherein each alternateroute is associated with a route identifier that identifies eachalternate route within the plurality of alternate routes; determining,by the mobile navigation device, the route identifier associated withthe alternate route determined for the remote vehicle; and whereintransmitting the route update data includes transmitting, to the remotemobile navigation device of the remote vehicle, the route identifierassociated with the alternate route determined for the remote vehicle.

Example 18 includes the subject matter of any of Examples 15-17, andfurther including receiving, by the mobile navigation device and fromthe remote mobile navigation device of the remote vehicle, one or moreof the plurality of alternate routes and the route identifier associatedwith each of the one or more of the plurality of alternate routesreceived; and wherein determining the alternate route and the associatedroute identifier for the remote vehicle includes determining thealternate route and the associated route identifier for the remotevehicle from the one or more alternate routes of the plurality ofalternate routes received from the remote mobile navigation device ofthe remote vehicle.

Example 19 includes the subject matter of any of Examples 15-18, andfurther including determining, by the mobile navigation device and inresponse to a determination of the occurrence of the reference trafficevent within the segment of the current route of the vehicle, analternate route for the vehicle to avoid the segment of the currentroute of the vehicle.

Example 20 includes the subject matter of any of Examples 15-19, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 21 includes the subject matter of any of Examples 15-20, andwherein generating the sensor data associated with the current route ofthe vehicle includes generating location data indicative of a currentlocation of the vehicle.

Example 22 includes the subject matter of any of Examples 15-21, andwherein generating the sensor data associated with the current route ofthe vehicle further includes generating traffic data indicative of acurrent traffic condition at the current location of the vehicle.

Example 23 includes the subject matter of any of Examples 15-22, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the vehicle, current weatherconditions at the current location of the vehicle, a traffic accident atthe current location of the vehicle, a roadway obstruction at thecurrent location of the vehicle, or a roadway hazard at the currentlocation of the vehicle.

Example 24 includes the subject matter of any of Examples 15-23, andwherein generating the traffic data indicative of the current trafficcondition includes generating traffic data indicative of a trafficaccident at the current location of the vehicle based on an analysis ofone or more images captured at the current location of the vehicle.

Example 25 includes the subject matter of any of Examples 15-24, andfurther including receiving, by the mobile navigation device and fromthe remote mobile navigation device of the remote vehicle, a request forroute data associated with a future route of the remote vehicle; andtransmitting, by the mobile navigation device and to the remote mobilenavigation device, the requested route data based on historical sensordata generated by the mobile navigation device for a past route of thevehicle.

Example 26 includes the subject matter of any of Examples 15-25, andwherein the mobile navigation device of the vehicle and the remotemobile navigation device are each member compute devices of a communitycloud; and wherein transmitting the route update data to the remotemobile navigation device includes transmitting the route update data tothe remote mobile navigation device of the community cloud.

Example 27 includes the subject matter of any of Examples 15-26, andfurther including preventing, by the mobile navigation device,transmission of the route update data to member compute devices of apublic cloud, wherein the public cloud is different from the communitycloud.

Example 28 includes the subject matter of any of Examples 15-27, andfurther including transmitting, by the mobile navigation device, thesensor data to a community compute device of the community cloud foranalysis.

Example 29 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including aprocessor; and a memory having stored therein a plurality ofinstructions that when executed by the processor cause the mobilenavigation device to perform the method of any of Examples 15-28.

Example 30 includes one or more machine-readable media including aplurality of instructions stored thereon that in response to beingexecuted result in a mobile navigation device of a vehicle performingthe method of any of Examples 15-28.

Example 31 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including means forgenerating sensor data associated with a current route of the vehicle,wherein at least a segment of the current route of the vehiclecorresponds to one or more segments of an existing route of a remotevehicle; means for determining, based on the generated sensor data, anoccurrence of a reference traffic event within the segment of thecurrent route of the vehicle; and means for transmitting route updatedata to a remote mobile navigation device of the remote vehicle inresponse to a determination of the occurrence of the reference trafficevent within the segment of the current route.

Example 32 includes the subject matter of Example 31, and furtherincluding means for generating, in response to a determination of theoccurrence of the reference traffic event within the segment of thecurrent route, an alternate route for the remote vehicle to avoid theone or more segments of the existing route of the remote vehicle thatcorrespond to the segment of the current route; and wherein the meansfor transmitting the route update data includes means for transmittingthe alternate route to the remote mobile navigation device of the remotevehicle.

Example 33 includes the subject matter of any of Examples 31 and 32, andfurther including means for determining, in response to a determinationof the occurrence of the reference traffic event within the segment ofthe current route, an alternate route of a plurality of alternate routesfor the remote vehicle to avoid the one or more segments of the existingroute of the remote vehicle that correspond to the segment of thecurrent route, wherein each alternate route is associated with a routeidentifier that identifies each alternate route within the plurality ofalternate routes; means for determining the route identifier associatedwith the alternate route determined for the remote vehicle; and whereinthe means for transmitting the route update data includes means fortransmitting, to the remote mobile navigation device of the remotevehicle, the route identifier associated with the alternate routedetermined for the remote vehicle.

Example 34 includes the subject matter of any of Examples 31-33, andfurther including means for receiving, from the remote mobile navigationdevice of the remote vehicle, one or more of the plurality of alternateroutes and the route identifier associated with each of the one or moreof the plurality of alternate routes received; and wherein the means fordetermining the alternate route and the associated route identifier forthe remote vehicle includes means for determining the alternate routeand the associated route identifier for the remote vehicle from the oneor more alternate routes of the plurality of alternate routes receivedfrom the remote mobile navigation device of the remote vehicle.

Example 35 includes the subject matter of any of Examples 31-34, andfurther including means for determining, in response to a determinationof the occurrence of the reference traffic event within the segment ofthe current route of the vehicle, an alternate route for the vehicle toavoid the segment of the current route of the vehicle.

Example 36 includes the subject matter of any of Examples 31-35, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 37 includes the subject matter of any of Examples 31-36, andwherein the means for generating the sensor data associated with thecurrent route of the vehicle includes means for generating location dataindicative of a current location of the vehicle.

Example 38 includes the subject matter of any of Examples 31-37, andwherein the means for generating the sensor data associated with thecurrent route of the vehicle further includes means for generatingtraffic data indicative of a current traffic condition at the currentlocation of the vehicle.

Example 39 includes the subject matter of any of Examples 31-38, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the vehicle, current weatherconditions at the current location of the vehicle, a traffic accident atthe current location of the vehicle, a roadway obstruction at thecurrent location of the vehicle, or a roadway hazard at the currentlocation of the vehicle.

Example 40 includes the subject matter of any of Examples 31-39, andwherein the means for generating the traffic data indicative of thecurrent traffic condition includes means for generating traffic dataindicative of a traffic accident at the current location of the vehiclebased on an analysis of one or more images captured at the currentlocation of the vehicle.

Example 41 includes the subject matter of any of Examples 31-40, andfurther including means for receiving, from the remote mobile navigationdevice of the remote vehicle, a request for route data associated with afuture route of the remote vehicle; and means for transmitting, to theremote mobile navigation device, the requested route data based onhistorical sensor data generated by the mobile navigation device for apast route of the vehicle.

Example 42 includes the subject matter of any of Examples 31-41, andwherein the mobile navigation device of the vehicle and the remotemobile navigation device are each member compute devices of a communitycloud; and wherein the means for transmitting the route update data tothe remote mobile navigation device includes means for transmitting theroute update data to the remote mobile navigation device of thecommunity cloud.

Example 43 includes the subject matter of any of Examples 31-42, andfurther including means for preventing transmission of the route updatedata to member compute devices of a public cloud, wherein the publiccloud is different from the community cloud.

Example 44 includes the subject matter of any of Examples 31-43, andfurther including means for transmitting the sensor data to a communitycompute device of the community cloud for analysis.

Example 45 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including a routedetermination module to (i) receive route update data from a membercompute device of a community cloud, the route update data determined inresponse to an occurrence of a reference traffic event within at leastone segment of a route of a remote vehicle, wherein the at least onesegment of the route of the remote vehicle corresponds to one or moresegments of a current route of the vehicle and (ii) update the currentroute of the vehicle to avoid the reference traffic event within the oneor more segments of the current route of the vehicle based on the routeupdate data received from the member compute device of the communitycloud.

Example 46 includes the subject matter of Example 45, and wherein theroute update data received from the member compute device of thecommunity cloud includes an alternate route generated to avoid thereference traffic event within the one or more segments of the currentroute of the vehicle; and wherein to update the current route of thevehicle includes to update the current route of the vehicle based on thealternate route.

Example 47 includes the subject matter of any of Examples 45 and 46, andwherein the route update data received from the member compute device ofthe community cloud includes a route identifier associated with analternate route of a plurality of alternate routes for the vehicle toavoid the reference traffic event within the one or more segments of thecurrent route of the vehicle, wherein each alternate route of theplurality of alternate routes for the vehicle is associated with adifferent route identifier; and wherein to update the current route ofthe vehicle includes to update the current route of the vehicle based onthe alternate route associated with the route identifier received fromthe member compute device of the community cloud.

Example 48 includes the subject matter of any of Examples 45-47, andwherein the route determination module is further to transmit, to themember compute device of the community cloud, one or more of theplurality of alternate routes and the different route identifierassociated with each of the one or more of the plurality of alternateroutes transmitted.

Example 49 includes the subject matter of any of Examples 45-48, andwherein the route update data received from the member compute device ofthe community cloud includes sensor data generated for the at least onesegment of the route of the remote vehicle within which the referencetraffic event occurs; and further including a route monitoring module todetermine, based on the sensor data, whether to generate an alternateroute to avoid the reference traffic event within the one or moresegments of the current route of the vehicle that correspond to theleast one segment of the route of the remote vehicle within which thereference traffic event occurs; wherein the route determination moduleis further to (i) generate the alternate route in response to adetermination to generate the alternate route to avoid the referencetraffic event within the one or more segments of the current route ofthe vehicle or (ii) transmit a request for the alternate route to themember compute device of the community cloud in response to adetermination not to generate the alternate route to avoid the referencetraffic event within the one or more segments of the current route ofthe vehicle and receive the alternate route from the member computedevice of the community cloud in response to the request; and wherein toupdate the current route of the vehicle includes to update the currentroute of the vehicle based on the alternate route generated by themobile navigation device or received from the member compute device ofthe community cloud.

Example 50 includes the subject matter of any of Examples 45-49, andwherein to determine whether to generate the alternate route based onthe sensor data includes to determine whether to generate the alternateroute based on the sensor data and at least one of an amount ofprocessing power required to generate the alternate route or an amountof remaining battery charge associated with the mobile navigationdevice.

Example 51 includes the subject matter of any of Examples 45-50, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 52 includes the subject matter of any of Examples 45-51, andwherein the route determination module is further to (i) transmit, tothe member compute device of the community cloud, a request for routedata associated with a future route of the vehicle and (ii) receive therequested route data from the member compute device of the communitycloud, wherein the requested route data generated based on historicalroute data associated with a past route of the remote vehicle.

Example 53 includes the subject matter of any of Examples 45-52, andwherein the member compute device includes a remote mobile navigationdevice of the remote vehicle.

Example 54 includes the subject matter of any of Examples 45-53, andwherein the member compute device includes a community compute device.

Example 55 includes the subject matter of any of Examples 45-54, andwherein the mobile navigation device of the vehicle and the membercompute device are each member compute devices of the community cloud.

Example 56 includes the subject matter of any of Examples 45-55, andfurther including a privacy management module to prevent reception ofthe route update data from member compute devices of a public cloud,wherein the public cloud is different from the community cloud.

Example 57 includes the subject matter of any of Examples 45-56, andwherein the route determination module is to (i) transmit a request forroute data associated with a future route of the vehicle to a cloudservice provider of a public cloud, wherein the public cloud isdifferent from the community cloud and (ii) receive the requested routedata from the cloud service provider of the public cloud, wherein therequested route data generated based on historical route data associatedwith a past route of a member compute device of a remote vehicle of thepublic cloud.

Example 58 includes a method for sharing route navigation data, themethod including receiving, by a mobile navigation device of a vehicle,route update data from a member compute device of a community cloud, theroute update data determined in response to an occurrence of a referencetraffic event within at least one segment of a route of a remotevehicle, wherein the at least one segment of the route of the remotevehicle corresponds to one or more segments of a current route of thevehicle; and updating, by the mobile navigation device, the currentroute of the vehicle to avoid the reference traffic event within the oneor more segments of the current route of the vehicle based on the routeupdate data received from the member compute device of the communitycloud.

Example 59 includes the subject matter of Example 58, and wherein theroute update data received from the member compute device of thecommunity cloud includes an alternate route generated to avoid thereference traffic event within the one or more segments of the currentroute of the vehicle; and wherein updating the current route of thevehicle includes updating the current route of the vehicle based on thealternate route.

Example 60 includes the subject matter of any of Examples 58 and 59, andwherein the route update data received from the member compute device ofthe community cloud includes a route identifier associated with analternate route of a plurality of alternate routes for the vehicle toavoid the reference traffic event within the one or more segments of thecurrent route of the vehicle, wherein each alternate route of theplurality of alternate routes for the vehicle is associated with adifferent route identifier; and wherein updating the current route ofthe vehicle includes updating the current route of the vehicle based onthe alternate route associated with the route identifier received fromthe member compute device of the community cloud.

Example 61 includes the subject matter of any of Examples 58-60, andfurther including transmitting, by the mobile navigation device and tothe member compute device of the community cloud, one or more of theplurality of alternate routes and the different route identifierassociated with each of the one or more of the plurality of alternateroutes transmitted.

Example 62 includes the subject matter of any of Examples 58-61, andwherein the route update data received from the member compute device ofthe community cloud includes sensor data generated for the at least onesegment of the route of the remote vehicle within which the referencetraffic event occurs; and further including determining, by the mobilenavigation device and based on the sensor data, whether to generate analternate route to avoid the reference traffic event within the one ormore segments of the current route of the vehicle that correspond to theleast one segment of the route of the remote vehicle within which thereference traffic event occurs; generating, by the mobile navigationdevice, the alternate route in response to a determination to generatethe alternate route to avoid the reference traffic event within the oneor more segments of the current route of the vehicle; transmitting, bythe mobile navigation device, a request for the alternate route to themember compute device of the community cloud in response to adetermination not to generate the alternate route to avoid the referencetraffic event within the one or more segments of the current route ofthe vehicle; receiving, by the mobile navigation device, the alternateroute from the member compute device of the community cloud in responseto the request; and wherein updating the current route of the vehicleincludes updating the current route of the vehicle based on thealternate route generated by the mobile navigation device or receivedfrom the member compute device of the community cloud.

Example 63 includes the subject matter of any of Examples 58-62, andwherein determining whether to generate the alternate route based on thesensor data includes determining whether to generate the alternate routebased on the sensor data and at least one of an amount of processingpower required to generate the alternate route or an amount of remainingbattery charge associated with the mobile navigation device.

Example 64 includes the subject matter of any of Examples 58-63, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 65 includes the subject matter of any of Examples 58-64, andfurther including transmitting, by the mobile navigation device and tothe member compute device of the community cloud, a request for routedata associated with a future route of the vehicle; and receiving, bythe mobile navigation device, the requested route data from the membercompute device of the community cloud, wherein the requested route datagenerated based on historical route data associated with a past route ofthe remote vehicle.

Example 66 includes the subject matter of any of Examples 58-65, andwherein the member compute device includes a remote mobile navigationdevice of the remote vehicle.

Example 67 includes the subject matter of any of Examples 58-66, andwherein the member compute device includes a community compute device.

Example 68 includes the subject matter of any of Examples 58-67, andwherein the mobile navigation device of the vehicle and the membercompute device are each member compute devices of the community cloud.

Example 69 includes the subject matter of any of Examples 58-68, andfurther including preventing, by the mobile navigation device, receptionof the route update data from member compute devices of a public cloud,wherein the public cloud is different from the community cloud.

Example 70 includes the subject matter of any of Examples 58-69, andfurther including transmitting, by the mobile navigation device, arequest for route data associated with a future route of the vehicle toa cloud service provider of a public cloud, wherein the public cloud isdifferent from the community cloud; and receiving, by the mobilenavigation device, the requested route data from the cloud serviceprovider of the public cloud, wherein the requested route data generatedbased on historical route data associated with a past route of a membercompute device of a remote vehicle of the public cloud.

Example 71 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including aprocessor; and a memory having stored therein a plurality ofinstructions that when executed by the processor cause the mobilenavigation device to perform the method of any of Examples 58-70.

Example 72 includes one or more machine-readable media including aplurality of instructions stored thereon that in response to beingexecuted result in a mobile navigation device of a vehicle performingthe method of any of Examples 58-70.

Example 73 includes a mobile navigation device of a vehicle for sharingroute navigation data, the mobile navigation device including means forreceiving route update data from a member compute device of a communitycloud, the route update data determined in response to an occurrence ofa reference traffic event within at least one segment of a route of aremote vehicle, wherein the at least one segment of the route of theremote vehicle corresponds to one or more segments of a current route ofthe vehicle; and means for updating the current route of the vehicle toavoid the reference traffic event within the one or more segments of thecurrent route of the vehicle based on the route update data receivedfrom the member compute device of the community cloud.

Example 74 includes the subject matter of Example 73, and wherein theroute update data received from the member compute device of thecommunity cloud includes an alternate route generated to avoid thereference traffic event within the one or more segments of the currentroute of the vehicle; and wherein the means for updating the currentroute of the vehicle includes means for updating the current route ofthe vehicle based on the alternate route.

Example 75 includes the subject matter of any of Examples 73 and 74, andwherein the route update data received from the member compute device ofthe community cloud includes a route identifier associated with analternate route of a plurality of alternate routes for the vehicle toavoid the reference traffic event within the one or more segments of thecurrent route of the vehicle, wherein each alternate route of theplurality of alternate routes for the vehicle is associated with adifferent route identifier; and wherein the means for updating thecurrent route of the vehicle includes means for updating the currentroute of the vehicle based on the alternate route associated with theroute identifier received from the member compute device of thecommunity cloud.

Example 76 includes the subject matter of any of Examples 73-75, andfurther including means for transmitting, to the member compute deviceof the community cloud, one or more of the plurality of alternate routesand the different route identifier associated with each of the one ormore of the plurality of alternate routes transmitted.

Example 77 includes the subject matter of any of Examples 73-76, andwherein the route update data received from the member compute device ofthe community cloud includes sensor data generated for the at least onesegment of the route of the remote vehicle within which the referencetraffic event occurs; and further including means for determining, basedon the sensor data, whether to generate an alternate route to avoid thereference traffic event within the one or more segments of the currentroute of the vehicle that correspond to the least one segment of theroute of the remote vehicle within which the reference traffic eventoccurs; means for generating the alternate route in response to adetermination to generate the alternate route to avoid the referencetraffic event within the one or more segments of the current route ofthe vehicle; means for transmitting a request for the alternate route tothe member compute device of the community cloud in response to adetermination not to generate the alternate route to avoid the referencetraffic event within the one or more segments of the current route ofthe vehicle; means for receiving the alternate route from the membercompute device of the community cloud in response to the request; andwherein the means for updating the current route of the vehicle includesmeans for updating the current route of the vehicle based on thealternate route generated by the mobile navigation device or receivedfrom the member compute device of the community cloud.

Example 78 includes the subject matter of any of Examples 73-77, andwherein the means for determining whether to generate the alternateroute based on the sensor data includes means for determining whether togenerate the alternate route based on the sensor data and at least oneof an amount of processing power required to generate the alternateroute or an amount of remaining battery charge associated with themobile navigation device.

Example 79 includes the subject matter of any of Examples 73-78, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 80 includes the subject matter of any of Examples 73-79, andfurther including means for transmitting, to the member compute deviceof the community cloud, a request for route data associated with afuture route of the vehicle; and means for receiving the requested routedata from the member compute device of the community cloud, wherein therequested route data generated based on historical route data associatedwith a past route of the remote vehicle.

Example 81 includes the subject matter of any of Examples 73-80, andwherein the member compute device includes a remote mobile navigationdevice of the remote vehicle.

Example 82 includes the subject matter of any of Examples 73-81, andwherein the member compute device includes a community compute device.

Example 83 includes the subject matter of any of Examples 73-82, andwherein the mobile navigation device of the vehicle and the membercompute device are each member compute devices of the community cloud.

Example 84 includes the subject matter of any of Examples 73-83, andfurther including means for preventing reception of the route updatedata from member compute devices of a public cloud, wherein the publiccloud is different from the community cloud.

Example 85 includes the subject matter of any of Examples 73-84, andfurther including means for transmitting a request for route dataassociated with a future route of the vehicle to a cloud serviceprovider of a public cloud, wherein the public cloud is different fromthe community cloud; and means for receiving the requested route datafrom the cloud service provider of the public cloud, wherein therequested route data generated based on historical route data associatedwith a past route of a member compute device of a remote vehicle of thepublic cloud.

Example 86 includes a community compute device for sharing routenavigation data, the community compute device including a communityroute monitoring module to (i) receive sensor data from a first mobilenavigation device of a first vehicle, the received sensor data isassociated with a current route of the first vehicle, and wherein atleast a segment of the current route of the first vehicle corresponds toone or more segments of a current route of a second vehicle and (ii)determine, based on the received sensor data, an occurrence of areference traffic event within the segment of the current route of thefirst vehicle; and a community route determination module to transmitroute update data to a second mobile navigation device of the secondvehicle in response to the determination of the occurrence of thereference traffic event within the segment of the current route of thefirst vehicle.

Example 87 includes the subject matter of Example 86, and wherein thecommunity route determination module is further to generate, in responseto the determination of the occurrence of the reference traffic eventwithin the segment of the current route of the first vehicle, analternate route for the second vehicle to avoid the one or more segmentsof the current route of the second vehicle that correspond to thesegment of the current route of the first vehicle; and wherein totransmit the route update data includes to transmit the alternate routeto the second mobile navigation device of the second vehicle.

Example 88 includes the subject matter of any of Examples 86 and 87, andwherein the community route determination module is further to (i)determine, in response to the determination of the occurrence of thereference traffic event within the segment of the current route of thefirst vehicle, an alternate route of a plurality of alternate routes forthe second vehicle to avoid the one or more segments of the currentroute of the second vehicle that correspond to the segment of thecurrent route of the first vehicle, wherein each alternate route isassociated with a route identifier that identifies each alternate routewithin the plurality of alternate routes and (ii) determine the routeidentifier associated with the alternate route determined for the secondvehicle; and wherein to transmit the route update data includes totransmit, to the second mobile navigation device of the second vehicle,the route identifier associated with the alternate route determined forthe second vehicle.

Example 89 includes the subject matter of any of Examples 86-88, andwherein the community route determination module is further to receive,from the second mobile navigation device of the second vehicle, one ormore of the plurality of alternate routes and the route identifierassociated with each of the one or more of the plurality of alternateroutes received; and wherein to determine the alternate route and theassociated route identifier for the second vehicle includes to determinethe alternate route and the associated route identifier for the secondvehicle from the one or more alternate routes of the plurality ofalternate routes received from the second mobile navigation device ofthe second vehicle.

Example 90 includes the subject matter of any of Examples 86-89, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 91 includes the subject matter of any of Examples 86-90, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle.

Example 92 includes the subject matter of any of Examples 86-91, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle and traffic data indicative of a current traffic condition atthe current location of the first vehicle.

Example 93 includes the subject matter of any of Examples 86-92, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the first vehicle, currentweather conditions at the current location of the first vehicle, atraffic accident at the current location of the first vehicle, a roadwayobstruction at the current location of the first vehicle, or a roadwayhazard at the current location of the first vehicle.

Example 94 includes the subject matter of any of Examples 86-93, andwherein the community route determination module is further to (i)receive, from the second mobile navigation device of the second vehicle,a request for route data associated with a future route of the secondvehicle, (ii) generate the requested route data based on historicalsensor data associated with a past route of the first vehicle, and (iii)transmit the generated route data to the second mobile navigationdevice.

Example 95 includes the subject matter of any of Examples 86-94, andwherein the community compute device, the first mobile navigationdevice, and the second mobile navigation device are each member computedevices of a community cloud; and wherein to transmit the route updatedata to the second mobile navigation device includes to transmit theroute update data to the second mobile navigation device of thecommunity cloud.

Example 96 includes the subject matter of any of Examples 86-95, andfurther including a community privacy management module to preventtransmission of the route update data to member compute devices of apublic cloud, wherein the public cloud is different from the communitycloud.

Example 97 includes a method for sharing route navigation data, themethod including receiving, by a community compute device, sensor datafrom a first mobile navigation device of a first vehicle, the receivedsensor data is associated with a current route of the first vehicle, andwherein at least a segment of the current route of the first vehiclecorresponds to one or more segments of a current route of a secondvehicle; determining, by the community compute device and based on thereceived sensor data, an occurrence of a reference traffic event withinthe segment of the current route of the first vehicle; and transmitting,by the community compute device, route update data to a second mobilenavigation device of the second vehicle in response to the determinationof the occurrence of the reference traffic event within the segment ofthe current route of the first vehicle.

Example 98 includes the subject matter of Example 97, and furtherincluding generating, by the community compute device and in response tothe determination of the occurrence of the reference traffic eventwithin the segment of the current route of the first vehicle, analternate route for the second vehicle to avoid the one or more segmentsof the current route of the second vehicle that correspond to thesegment of the current route of the first vehicle; and whereintransmitting the route update data includes transmitting the alternateroute to the second mobile navigation device of the second vehicle.

Example 99 includes the subject matter of any of Examples 97 and 98, andfurther including determining, by the community compute device and inresponse to the determination of the occurrence of the reference trafficevent within the segment of the current route of the first vehicle, analternate route of a plurality of alternate routes for the secondvehicle to avoid the one or more segments of the current route of thesecond vehicle that correspond to the segment of the current route ofthe first vehicle, wherein each alternate route is associated with aroute identifier that identifies each alternate route within theplurality of alternate routes; determining, by the community computedevice, the route identifier associated with the alternate routedetermined for the second vehicle; and wherein transmitting the routeupdate data includes transmitting, to the second mobile navigationdevice of the second vehicle, the route identifier associated with thealternate route determined for the second vehicle.

Example 100 includes the subject matter of any of Examples 97-99, andfurther including receiving, by the community compute device and fromthe second mobile navigation device of the second vehicle, one or moreof the plurality of alternate routes and the route identifier associatedwith each of the one or more of the plurality of alternate routesreceived; and wherein determining the alternate route and the associatedroute identifier for the second vehicle includes determining thealternate route and the associated route identifier for the secondvehicle from the one or more alternate routes of the plurality ofalternate routes received from the second mobile navigation device ofthe second vehicle.

Example 101 includes the subject matter of any of Examples 97-100, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 102 includes the subject matter of any of Examples 97-101, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle.

Example 103 includes the subject matter of any of Examples 97-102, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle and traffic data indicative of a current traffic condition atthe current location of the first vehicle.

Example 104 includes the subject matter of any of Examples 97-103, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the first vehicle, currentweather conditions at the current location of the first vehicle, atraffic accident at the current location of the first vehicle, a roadwayobstruction at the current location of the first vehicle, or a roadwayhazard at the current location of the first vehicle.

Example 105 includes the subject matter of any of Examples 97-104, andfurther including receiving, by the community compute device and fromthe second mobile navigation device of the second vehicle, a request forroute data associated with a future route of the second vehicle;generating, by the community compute device, the requested route databased on historical sensor data associated with a past route of thefirst vehicle; and transmitting, by the community compute device, thegenerated route data to the second mobile navigation device.

Example 106 includes the subject matter of any of Examples 97-105, andwherein the community compute device, the first mobile navigationdevice, and the second mobile navigation device are each member computedevices of a community cloud; and wherein transmitting the route updatedata to the second mobile navigation device includes transmitting theroute update data to the second mobile navigation device of thecommunity cloud.

Example 107 includes the subject matter of any of Examples 97-106, andfurther including preventing, by the community compute device,transmission of the route update data to member compute devices of apublic cloud, wherein the public cloud is different from the communitycloud.

Example 108 includes a community compute device for sharing routenavigation data, the community compute device including a processor; anda memory having stored therein a plurality of instructions that whenexecuted by the processor cause the community compute device to performthe method of any of Examples 97-107.

Example 109 includes one or more machine-readable media including aplurality of instructions stored thereon that in response to beingexecuted result in a community compute device performing the method ofany of Examples 97-107.

Example 110 includes a community compute device for sharing routenavigation data, the community compute device including means forreceiving sensor data from a first mobile navigation device of a firstvehicle, the received sensor data is associated with a current route ofthe first vehicle, and wherein at least a segment of the current routeof the first vehicle corresponds to one or more segments of a currentroute of a second vehicle; means for determining, based on the receivedsensor data, an occurrence of a reference traffic event within thesegment of the current route of the first vehicle; and means fortransmitting route update data to a second mobile navigation device ofthe second vehicle in response to the determination of the occurrence ofthe reference traffic event within the segment of the current route ofthe first vehicle.

Example 111 includes the subject matter of Example 110, and furtherincluding means for generating, in response to the determination of theoccurrence of the reference traffic event within the segment of thecurrent route of the first vehicle, an alternate route for the secondvehicle to avoid the one or more segments of the current route of thesecond vehicle that correspond to the segment of the current route ofthe first vehicle; and wherein the means for transmitting the routeupdate data includes means for transmitting the alternate route to thesecond mobile navigation device of the second vehicle.

Example 112 includes the subject matter of any of Examples 110 and 111,and further including means for determining, in response to thedetermination of the occurrence of the reference traffic event withinthe segment of the current route of the first vehicle, an alternateroute of a plurality of alternate routes for the second vehicle to avoidthe one or more segments of the current route of the second vehicle thatcorrespond to the segment of the current route of the first vehicle,wherein each alternate route is associated with a route identifier thatidentifies each alternate route within the plurality of alternateroutes; means for determining the route identifier associated with thealternate route determined for the second vehicle; and wherein the meansfor transmitting the route update data includes means for transmitting,to the second mobile navigation device of the second vehicle, the routeidentifier associated with the alternate route determined for the secondvehicle.

Example 113 includes the subject matter of any of Examples 110-112, andfurther including means for receiving, from the second mobile navigationdevice of the second vehicle, one or more of the plurality of alternateroutes and the route identifier associated with each of the one or moreof the plurality of alternate routes received; and wherein the means fordetermining the alternate route and the associated route identifier forthe second vehicle includes means for determining the alternate routeand the associated route identifier for the second vehicle from the oneor more alternate routes of the plurality of alternate routes receivedfrom the second mobile navigation device of the second vehicle.

Example 114 includes the subject matter of any of Examples 110-113, andwherein the reference traffic event includes at least one of a referenceamount of traffic congestion, a reference type of traffic accident, areference amount of roadway construction, a reference roadwayobstruction, or a reference roadway hazard.

Example 115 includes the subject matter of any of Examples 110-114, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle.

Example 116 includes the subject matter of any of Examples 110-115, andwherein the sensor data received from the first mobile navigation deviceincludes location data indicative of a current location of the firstvehicle and traffic data indicative of a current traffic condition atthe current location of the first vehicle.

Example 117 includes the subject matter of any of Examples 110-116, andwherein the current traffic condition includes at least one of a currenttraffic flow at the current location of the first vehicle, currentweather conditions at the current location of the first vehicle, atraffic accident at the current location of the first vehicle, a roadwayobstruction at the current location of the first vehicle, or a roadwayhazard at the current location of the first vehicle.

Example 118 includes the subject matter of any of Examples 110-117, andfurther including means for receiving, from the second mobile navigationdevice of the second vehicle, a request for route data associated with afuture route of the second vehicle; means for generating the requestedroute data based on historical sensor data associated with a past routeof the first vehicle; and means for transmitting the generated routedata to the second mobile navigation device.

Example 119 includes the subject matter of any of Examples 110-118, andwherein the community compute device, the first mobile navigationdevice, and the second mobile navigation device are each member computedevices of a community cloud; and wherein the means for transmitting theroute update data to the second mobile navigation device includes meansfor transmitting the route update data to the second mobile navigationdevice of the community cloud.

Example 120 includes the subject matter of any of Examples 110-119, andfurther including means for preventing transmission of the route updatedata to member compute devices of a public cloud, wherein the publiccloud is different from the community cloud.

1. A community compute device for sharing route navigation data, thecommunity compute device comprising: a community route monitoring moduleto (i) receive sensor data from a first mobile navigation device of afirst vehicle, the received sensor data is associated with a currentroute of the first vehicle, and wherein at least a segment of thecurrent route of the first vehicle corresponds to one or more segmentsof a current route of a second vehicle and (ii) determine, based on thereceived sensor data, an occurrence of a reference traffic event withinthe segment of the current route of the first vehicle; and a communityroute determination module to transmit route update data to a secondmobile navigation device of the second vehicle in response to thedetermination of the occurrence of the reference traffic event withinthe segment of the current route of the first vehicle.
 2. The communitycompute device of claim 1, wherein the community route determinationmodule is further to generate, in response to the determination of theoccurrence of the reference traffic event within the segment of thecurrent route of the first vehicle, an alternate route for the secondvehicle to avoid the one or more segments of the current route of thesecond vehicle that correspond to the segment of the current route ofthe first vehicle; and wherein to transmit the route update datacomprises to transmit the alternate route to the second mobilenavigation device of the second vehicle.
 3. The community compute deviceof claim 1, wherein the community route determination module is furtherto (i) determine, in response to the determination of the occurrence ofthe reference traffic event within the segment of the current route ofthe first vehicle, an alternate route of a plurality of alternate routesfor the second vehicle to avoid the one or more segments of the currentroute of the second vehicle that correspond to the segment of thecurrent route of the first vehicle, wherein each alternate route isassociated with a route identifier that identifies each alternate routewithin the plurality of alternate routes and (ii) determine the routeidentifier associated with the alternate route determined for the secondvehicle; and wherein to transmit the route update data comprises totransmit, to the second mobile navigation device of the second vehicle,the route identifier associated with the alternate route determined forthe second vehicle.
 4. The community compute device of claim 3, whereinthe community route determination module is further to receive, from thesecond mobile navigation device of the second vehicle, one or more ofthe plurality of alternate routes and the route identifier associatedwith each of the one or more of the plurality of alternate routesreceived; and wherein to determine the alternate route and theassociated route identifier for the second vehicle comprises todetermine the alternate route and the associated route identifier forthe second vehicle from the one or more alternate routes of theplurality of alternate routes received from the second mobile navigationdevice of the second vehicle.
 5. The community compute device of claim4, wherein the reference traffic event comprises at least one of areference amount of traffic congestion, a reference type of trafficaccident, a reference amount of roadway construction, a referenceroadway obstruction, or a reference roadway hazard.
 6. The communitycompute device of claim 4, wherein the sensor data received from thefirst mobile navigation device comprises location data indicative of acurrent location of the first vehicle.
 7. The community compute deviceof claim 4, wherein the sensor data received from the first mobilenavigation device comprises location data indicative of a currentlocation of the first vehicle and traffic data indicative of a currenttraffic condition at the current location of the first vehicle.
 8. Thecommunity compute device of claim 7, wherein the current trafficcondition comprises at least one of a current traffic flow at thecurrent location of the first vehicle, current weather conditions at thecurrent location of the first vehicle, a traffic accident at the currentlocation of the first vehicle, a roadway obstruction at the currentlocation of the first vehicle, or a roadway hazard at the currentlocation of the first vehicle.
 9. The community compute device of claim4, wherein the community route determination module is further to (i)receive, from the second mobile navigation device of the second vehicle,a request for route data associated with a future route of the secondvehicle, (ii) generate the requested route data based on historicalsensor data associated with a past route of the first vehicle, and (iii)transmit the generated route data to the second mobile navigationdevice.
 10. One or more machine-readable media comprising a plurality ofinstructions stored thereon that in response to being executed cause acommunity compute device to: receive sensor data from a first mobilenavigation device of a first vehicle, the received sensor data isassociated with a current route of the first vehicle, and wherein atleast a segment of the current route of the first vehicle corresponds toone or more segments of a current route of a second vehicle; determine,based on the received sensor data, an occurrence of a reference trafficevent within the segment of the current route of the first vehicle; andtransmit route update data to a second mobile navigation device of thesecond vehicle in response to the determination of the occurrence of thereference traffic event within the segment of the current route of thefirst vehicle.
 11. The one or more machine-readable media of claim 10,wherein the plurality of instructions further cause the communitycompute device to generate, in response to the determination of theoccurrence of the reference traffic event within the segment of thecurrent route of the first vehicle, an alternate route for the secondvehicle to avoid the one or more segments of the current route of thesecond vehicle that correspond to the segment of the current route ofthe first vehicle; and wherein to transmit the route update datacomprises to transmit the alternate route to the second mobilenavigation device of the second vehicle.
 12. The one or moremachine-readable media of claim 10, wherein the plurality ofinstructions further cause the community compute device to: determine,in response to the determination of the occurrence of the referencetraffic event within the segment of the current route of the firstvehicle, an alternate route of a plurality of alternate routes for thesecond vehicle to avoid the one or more segments of the current route ofthe second vehicle that correspond to the segment of the current routeof the first vehicle, wherein each alternate route is associated with aroute identifier that identifies each alternate route within theplurality of alternate routes; and determine the route identifierassociated with the alternate route determined for the second vehicle;and wherein to transmit the route update data comprises to transmit, tothe second mobile navigation device of the second vehicle, the routeidentifier associated with the alternate route determined for the secondvehicle.
 13. The one or more machine-readable media of claim 12, whereinthe plurality of instructions further cause the community compute deviceto receive, from the second mobile navigation device of the secondvehicle, one or more of the plurality of alternate routes and the routeidentifier associated with each of the one or more of the plurality ofalternate routes received; and wherein to determine the alternate routeand the associated route identifier for the second vehicle comprises todetermine the alternate route and the associated route identifier forthe second vehicle from the one or more alternate routes of theplurality of alternate routes received from the second mobile navigationdevice of the second vehicle.
 14. The one or more machine-readable mediaof claim 13, wherein the reference traffic event comprises at least oneof a reference amount of traffic congestion, a reference type of trafficaccident, a reference amount of roadway construction, a referenceroadway obstruction, or a reference roadway hazard.
 15. The one or moremachine-readable media of claim 13, wherein the sensor data receivedfrom the first mobile navigation device comprises location dataindicative of a current location of the first vehicle.
 16. A method forsharing route navigation data, the method comprising: receiving, by acommunity compute device, sensor data from a first mobile navigationdevice of a first vehicle, the received sensor data is associated with acurrent route of the first vehicle, and wherein at least a segment ofthe current route of the first vehicle corresponds to one or moresegments of a current route of a second vehicle; determining, by thecommunity compute device and based on the received sensor data, anoccurrence of a reference traffic event within the segment of thecurrent route of the first vehicle; and transmitting, by the communitycompute device, route update data to a second mobile navigation deviceof the second vehicle in response to the determination of the occurrenceof the reference traffic event within the segment of the current routeof the first vehicle.
 17. The method of claim 16, further comprising:generating, by the community compute device and in response to thedetermination of the occurrence of the reference traffic event withinthe segment of the current route of the first vehicle, an alternateroute for the second vehicle to avoid the one or more segments of thecurrent route of the second vehicle that correspond to the segment ofthe current route of the first vehicle; and wherein transmitting theroute update data comprises transmitting the alternate route to thesecond mobile navigation device of the second vehicle.
 18. The method ofclaim 16, further comprising: determining, by the community computedevice and in response to the determination of the occurrence of thereference traffic event within the segment of the current route of thefirst vehicle, an alternate route of a plurality of alternate routes forthe second vehicle to avoid the one or more segments of the currentroute of the second vehicle that correspond to the segment of thecurrent route of the first vehicle, wherein each alternate route isassociated with a route identifier that identifies each alternate routewithin the plurality of alternate routes; determining, by the communitycompute device, the route identifier associated with the alternate routedetermined for the second vehicle; and wherein transmitting the routeupdate data comprises transmitting, to the second mobile navigationdevice of the second vehicle, the route identifier associated with thealternate route determined for the second vehicle.
 19. The method ofclaim 18, further comprising receiving, by the community compute deviceand from the second mobile navigation device of the second vehicle, oneor more of the plurality of alternate routes and the route identifierassociated with each of the one or more of the plurality of alternateroutes received; and wherein determining the alternate route and theassociated route identifier for the second vehicle comprises determiningthe alternate route and the associated route identifier for the secondvehicle from the one or more alternate routes of the plurality ofalternate routes received from the second mobile navigation device ofthe second vehicle.
 20. The method of claim 16, wherein the referencetraffic event comprises at least one of a reference amount of trafficcongestion, a reference type of traffic accident, a reference amount ofroadway construction, a reference roadway obstruction, or a referenceroadway hazard.